home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
jmsts20.zip
/
JMSTATS.DOC
< prev
next >
Wrap
Text File
|
1993-02-06
|
42KB
|
1,123 lines
JMSTATS! ver 2.0
for Wildcat! BBS systems
written by Joe Martin
copyright 1992
JMSTATS is a complete analyzer of the Activity logs that are
produced by Wildcat!. This one program will read the activity logs
created by either version 3.55 or 2.55 depending on the command line
you use and store that information for use in later displays. If
you have tried to review your activity log file like I have, you
have probably found that it is great if you are looking at one
specific thing at a time, but useless if you are interested in
getting any kind of analysis of what is happening on the BBS on a
long term basis. The activity log files take up a lot of room, and
with a single line or more for each activity, a very active person
can take up multiple screens of information in a single call.
Well, no more will you have to settle for this. JMSTATS will
read these activity logs and compile them into output files that can
be looked at and interpreted at a glance. This program has been
designed to be efficient and easily configurable by the sysop to
meet his needs. Since each Wildcat! BBS is distinctive, so should
the program that analyzes the BBS be. No need to settle for a
predefined display that only gives you part of what you need.
This program was conceived by a need I had of trying to
determine what was happening on my board over a period of time. I
have incorporated as many features as I could think of and will add
more if there is a need. Now, by looking at a couple of displays, a
sysop can get a really good feel of what is happening on their
board.
JMSTATS is written in Turbo Pascal and is designed to be very
fast. There is the capability of having multiple configuration
files so that the data can be collected and output in various
manners. I will try to go through all the ideas that I would like
this program to do as it progresses, and I am anxious to hear from
others whether it fits their needs or if there are some other things
that I can accomplish with the program. The final outcome of this
program will depend on what YOU, the sysops, would like to see it
become. I have added in everything I can think of, but I am sure
there are others with even better ideas.
That about covers the general scope and ideals of the program,
now I will get on to some of the features and uses of the program.
1
JMSTATS ver 2.0
DISCLAIMER
This software is provided without any guarantee, either
expressed or implied. All responsibilities for its use rest with
the user of the software and not the author.
JMSTATS software and this document are (C) Copyright 1993
by Joe Martin. All rights reserved World Wide.
2
JMSTATS ver 2.0
LICENSE
JMSTATS is not in the Public Domain. JMSTATS is not free.
Non-registered users are granted a limited, 30-day license to
determine whether or not the program meets their needs. Continued
use of JMSTATS beyond the 30-day evaluation time period requires
registration of the program. Use of non-registered copies of
JMSTATS beyond the original evaluation period is strictly
prohibited. No one may modify JMSTATS for any reason, in any way,
including but not limited to decompiling-compiling, patching,
disassembling, or reverse engineering the program. JMSTATS may be
copied and distributed to others, subject to the above restrictions
and the following:
* JMSTATS must be copied in unmodified form, including the
file containing this license information.
* Complete JMSTATS documentation must be included.
* No copying fee of any type may be assessed other than basic
charges for the cost of the copying medium.
* JMSTATS may not be distributed with any other software or
hardware product(s) without the express written permission
of Joe Martin.
Sysops (bulletin board SYStem OPerators) may make JMSTATS
available for downloading by their users as long as all above
conditions are met.
Commercial Distributors of Public Domain, ShareWare, or User
Supported software may distribute JMSTATS subject to the above
conditions only after obtaining specific written permission from Joe
Martin and filling out a registration form for upgrade
notifications. This condition supersedes any and all previous
agreements.
3
JMSTATS ver 2.0
FEATURES
Program operation is handled by using configuration files to set
up the program to fit the needs of your BBS.
Multiple configuration files that allow you to display the data
differently or store it in different areas. These multiple
configuration files can be used to read the activity log files from
different nodes on a multi-node BBS. They can also be used to store
the data in different directories for providing different criteria
such as different length of time to keep the data. For example, you
may have a subdirectory called WEEKLY and one called MONTHLY and
each can store the data for the previous week or month. This way,
you can tell if things are changing on the board and where your
board is improving or lacking.
Configuration of multiple baud rates to be used in the DOWNLOAD
display file. The configuration will accept up to 8 baud rates, but
4 is recommended if you plan on using this file for display on a BBS
or on your screen. You can choose the most popular baud rates on
your BBS, whether you have high speed modems or not.
Configuration of multiple file transfer protocols to be used in
the DOWNLOAD display file. The configuration file will allow you to
enter up to 10 transfer protocols and will include all others not
entered in a general grouping called OTHER PROTOCOLS. If you are
using this file for display on a BBS or on a screen and wish to keep
it to a single screen, then I would recommend including only 5
transfer protocols and letting the rest be included in the OTHER
PROTOCOLS.
Command line switch to not display MNP connections. This would be
very useful for those sysops who do not have an error-correcting
modem and thus would never have any use for display connections with
MNP.
Configuration of Minimum and Maximum transfer CPS to prevent the
DOWNLOAD display from using erroneous figures in calculating the
average cps for a protocol or as the minimum or maximum cps in the
display. These are entered as a percentage of the optimum transfer
rate. For example, at 2400 baud, the optimum as determined by most
terminal and BBS programs would be 240 cps. If you use a minimum
percentage of 50, the program will calculate the minimum cps to
accept as 50% of 240 cps which would be 120 cps. The same is true
for the maximum percentage. If you configure it for a maximum of
150, at 2400 baud it would be 150% of 240 which would be 360 cps.
Between these two figures, you can set the limits as to what is
included in the DOWNLOAD display file.
Display file output can be automatically configured to go to the
screen by leaving the output path and filename as BLANK. It can
also be directed to the printer by entering "PRN" as the output file
name. This can be very handy if you want to have one configuration
that includes all of your file transfer protocols or bauds and you
have a printer that can handle the size of the report.
Exclude files for certain routines to allow the sysop to exclude
certain file areas or security levels from showing up. This would
4
JMSTATS ver 2.0
prevent a display from showing areas or filenames that some sysops
do not want displayed to the general caller, but may want to display
when he looks at it.
A display file that shows the various activity levels by the
security level of the callers. This will let a sysop determine how
good or bad certain security levels are. For example, are your
callers with a visiting sysop security level spending more time
downloading files than your subscribing members?
A display file showing various activities sorted by the hour of
the day. This display can be very useful in determining what is
being used most on your board during certain times of the day.
There is also a Door Game usage display that will show the number
of times a door is entered, how much time has been spent in the door
and also the average time spent in the door. This display can be
sorted by any of the above fields.
A file download history display that will allow you to enter a
filename and get a listing of everyone who has downloaded that
particular file. This is one of the best features of the program in
my judgement. A couple of uses for this would be to either notify
all users that have downloaded a particular file in the event you
found that the file was corrupted or had a virus in it or maybe to
get a listing of all the callers that have downloaded your
registration form.
A caller display that will give you loads of pertinent
information about a particular caller. It will display the number of
calls, uploads, downloads, fast logins, pages and so on. In
addition, it will list the name of every file that person has
uploaded and also a list of every file that they have downloaded.
This way you can get a good, overall picture of what a particular
caller has been doing with their on-line time.
Colors are being used by some of the displays and the actual
colors are stored in a separate file. This file can be set up using
either the WildCat! @ codes or can contain ANSI codes, whichever the
sysop prefers. I have included a sample DISPLAY.CLR file with the
program as an example. If you do not wish to use color codes, either
change the file or remove it.
5
JMSTATS ver 2.0
OPERATION
I would suggest creating a directory called something similar
to JMSTATS so that you can keep all the files together. Unzip this
file and put all of the files into this directory that were created
from the ZIP file. Then type in JMSTAT -CFG in order to change the
JMSTAT.CFG file to match the setup needed for operation on your
board. You can also change the name of the config file in order to
create multiple configurations. Do this for each configuration that
you will need to use. I have included an example config (JMSTAT.CFG)
in this archive.
I have also included some sample output files (those with names
ending in .BBS and .CLR) for you to see what the displays will look
like.
This program can be run either by using switches on the command
line after the name of the program or by just keying in JMSTAT to
bring up a menu. If you wish to use a configuration file other than
"JMSTAT.CFG", you must include it as a parameter before the parameters
that will be using that configuration file. If the name of the
configuration file is left off, the system will automatically use the
JMSTAT.CFG file. If the configuration file is not found, the program
will error out.
All other switches must be preceded by the '-' in order for the
program to read them. Some switches will have only one letter while
others can include other needed information immediately following
the '-' or even multiple switches in a single parameter for passing
such things as sorting options or dates. A listing of the valid
switches is as follows:
6
JMSTATS ver 2.0
SWITCHES
(note...optional paramters are enclosed in square brackets.)
(-days is an option that could either be a starting date, a number of
days prior to today or the letter M which would be just the current
month's information).
-A[-days].....This switch will create a display file of both your
file areas and message areas and shows you how many times
files have been downloaded from certain file areas and how
many messages are left in certain message areas. This file
is automatically sorted by usage so it is easy to determine
what areas of your board are the most popular. The current
maximum is 3000 file areas and/or 3000 message areas. The
optional days can be added to the command in order to limit
the display to a certain time period.
-C-callername[-days].....This switch followed by a caller's name will
create a display file for an individual caller. The program
will locate the first caller that matches what you have
entered, so you must include enough so that it will display
the proper caller. If you need to include a space in the
caller's name to
narrow it down, this can be done by replacing the space with
an underscore '_' character on the command line. The program
will automatically convert this to a space. It will display
the general stats for that caller including such things as
number of calls, number of doors, time spent in doors, number
of uploads, number and name of all files that this caller has
uploaded and downloaded, plus many other statistics relating
to that caller. What would you like to have included in this?
The -days option can be added to limit the display to a
certain time period.
-D[-days-NO] .....This switch tells the program to create the
DOWNLOAD display file from the data already collected and
output it to what is set up in the config file. The 'NO'
part tells the program to not print any MNP lines. This is
especially useful for those with non error-correcting
modems and will allow for twice as many protocols on the
screen. The days command can be added in order to limit the
display to a certain time period.
-F-filename[-days] .....This switch will produce a report of everyone
who has downloaded a particular file and when. You must
include the filename immediately following the -F. This can be
particularly useful if for example you find out that one of
your files contains a new virus that was not picked up during
an initial virus scan. It will make it very simple to find out
who has downloaded this file and notify them. Now that is what
I would call a conscientious sysop. The days command can be
added in order to limit the display to a certain time period.
7
JMSTATS ver 2.0
-G[-days-xx] ....This switch will produce a display of the door game
statistics. It will include the door numbers, times entered,
total and average time spent in each door game. This will
help you in determining which doors are most popular and
which may need to be removed due to lack of use. The current
limit for # of doors is 29. The 'xx' stands for an
additional sort parameter. The options for xx are as
follows:
U ...sort by times Used
A ...sort by average time in door
T ...sort by total time in door
-H .....This switch will bring up a short listing of the command
options that are available.
-O[-days] .....This switch will reorganize the database files. The JDM
files must first be sorted using any text file sorting program
you wish. I find that QSORT by Ben Baker to do these sorts
extremely fast. This switch will remove any duplicate lines
from the database files. This will only need to be used if
for some reason you read the same activity log more than one
time, or if the database files get messed up with a bad date
on the system or something like that. The days command may be
used to clear out all entries older than a certain date.
-R[-xxx] .....This tells the program to read the activity log file that
you have set up in the config file and add the information
into the database files. That is all the program will do with
that switch and will produce no output at that point. For
those sysops who are using Tomcat! for NetMail and do not wish
the messages uploaded by these netsysops to be included in
your message information, you can exclude up to 20 security
levels by putting them in a file called EXCLUDE.NET. This file
should contain the exact security levels you do not wish to be
included in the message statistics (including capitalization).
The program will check for the existence of this file and will
build all other statistics except the messages database for
these callers. The optional field (xxx) will accept the value
'255' and will then be able to read the activity logs created
by WildCat! version 2.55. This currently has limited support
because I have only had one activity log file to look at from
that release.
-S[-days-xx] .....This switch tells the program to create the SECURITY
display file from the data already collected and output it to
that is set up in the config file. The current limit of # of
security levels is 29. The xx part is optional and will
determine the sorting of the security display file. xx may
consist of the following:
DL ...sort by number of downloads
UL ...sort by number of uploads
FL ...sort by number of Fast Logins
NF ...sort by number of New file scans
8
JMSTATS ver 2.0
TU ...sort by number of Tomcat Uploads
TD ...sort by number of Tomcat Downloads
P ...sort by number of sysop Pages
M ...sort by number of Messages
G ...sort by number of door Games entered
TC ...sort by number of total calls
AV ...sort by Average time per call
TM ...sort by Total Minutes
There is also an additional feature of this display and
that is the ability to EXCLUDE certain security levels from
your display. To do this, create a file called EXCLUDE.SEC
in the directory that you are running the JMSTATS program
from. Each line of this file would be a security level
exactly as it appears in your Activity log. This includes
capital letters. Any security level found in this file will
not be reported by the security display file. I have
included an example of a EXCLUDE.SEC file you to see how it
is set up.
-T[-days] .....This switch tells the program to create the Time of Day
display file. This is a complete display by the hour of the
day that will tell you what happened each hour. This includes
# of calls, messages, doors, uploads, downloads, pages, etc.
The output will be directed to what is set up in the Config
file. The optional days command will limit the display to a
certain time period.
-TF[-days-exclude.fil] .....This switch will produce a top 45 download
file listing. In addition, it will allow you the ability via
an external EXCLUDE file to not print statistics for certain
file areas. This could be especially useful if you have Adult
file areas on the board and do not wish to include them in
your top files listing. The default file name that should
contain the number of the file areas to exclude is
EXCLUDE.FIL. A different filename can be specified on the
command line in place of the exclude.fil file. The program
currently allows up to 30 file areas to be excluded by putting
the file area numbers into the EXCLUDE.FIL using one file area
per line. An example EXCLUDE.FIL is included in this package.
Be sure to review it and either delete it or change it to fit
the needs of your BBS. The days command can be used to limit
the display to a certain time period.
-TC[-days] .....This switch will create a display file that will show
the top 15 callers. There are 3 columns, one for the top
caller, one for the top message poster and one for the top
uploader. Each column is separate so they can contain
different caller names. The days command can be added to limit
the display to a certain time period.
-TD[-days] .....This switch will create a display file that will show
up to 45 callers sorted by the number of files they have
downloaded. This can give you an idea of who your main file
grabbers are. The days command can be added to limit the
display to a certain time period.
9
JMSTATS ver 2.0
-CFG .....This switch will allow you to create or modify the
configuration files used by the JMSTATS program. All fields
are accessible using this command to make it easy to install
the program for the first time.
If you wish to change to a different configuration file within the
program, just put the name of the new configuration file on the command
line and all parameters after that will use this new configuration
file. Unlimited number of configurations can be set up to be used.
These switches may be combined on one command line and will be
performed in the order that they are entered. Multiple switches can
and are recommended to be included on the command line. Below are some
examples of how to use this command line operation to achieve the
desired results.
10
JMSTATS ver 2.0
SAMPLES
Let's assume that you are running a single line Wildcat! BBS
and wish to use only the DOWNLOAD display file as bulletin #1 on
your board. First, make sure you have the JMSTAT.CFG file set up to
match the paths and needs of your system. Let us also assume that
you will be running this program in your nightly event batch
program. This is the way you would use the program.
NIGHTLY.BAT
CD \JMSTATS
JMSTAT JMSTAT.CFG -R -D
(this could also be written as follows)
JMSTAT -R -D
(since the config file name of JMSTAT.CFG is the default)
That is all that is needed to run on a single line system. If
you would also like to have it prepare the SECURITY display file,
but just keep it in the JMSTATS directory for your own use, then be
sure to set the path correctly in the config file and use the
following command.
CD \JMSTATS
JMSTAT JMSTAT.CFG -R -D -S
The -r will build the database from your activity log file. The
-d will build the DOWNLOAD display file based on the information
calculated with the first -r switch. The -s switch will build the
SECURITY display file in a similar manner.
Starting with version 2.0 of JMSTATS, there is no longer a need to
remove your activity logs once they have been read by the program. The
files called LASTLINE.??? (where the ??? is the same as the extension
of the activity log that you are reading into the database) contains
the date and time of the last entry. Therefore, the -r option will
start to read the data following this date and time. If you ever have a
need to actually reread the same activity log file, just delete the
LASTLINE.??? file for the log you wish to read in.
For a multi line system that has more than one activity log but
the sysop wishes to include the data from all nodes into the
database files that the reports are built from, then you will have
to make separate config files for each node. Since the config file
includes the full file name that it will read in to include, you
would have to have something like JMSTAT1.CFG to read in node 1,
JMSTAT2.CFG to read in node 2, and so on. Then, your nightly batch
file to read the data from both nodes and combine them into one
database and prepare both the DOWNLOAD and SECURITY files would look
like this:
NIGHTLY.BAT
CD \JMSTATS
JMSTAT JMSTAT1.CFG -R
11
JMSTATS ver 2.0
JMSTAT JMSTAT2.CFG -R -D -S
or with version 2.0 and above, you could do the following:
CD \JMSTATS
JMSTAT JMSTAT1.CFG -R JMSTAT2.CFG -R -D -S
since multiple configuration files on one command line are now allowed.
The first time the program is called, it only reads the
information from the activity log for node 1 into the database. The
second time the program is called, it reads in the information from
the activity log for node 2, then it processes and creates the
DOWNLOAD and SECURITY display files. For more than 2 nodes, you
would just run the program once for each node using just the -r
switch but include the -d and -s switches when running the program
on the last node to be included.
To clear the database files, you would first use the -r switch
to read in the latest data. Then you would use a sorting program
like QSORT by Ben Baker or any other that you prefer, then use the
-o switch to clean up the database files. To clear out old records,
include a date or a number of days after the -o. Here is an example
of how this would work.
CD \JMSTATS
JMSTAT JMSTAT.CFG -R
QSORT CALLS.JDM
QSORT MESSAGES.JDM
QSORT DOWNLOADS.JDM
QSORT UPLOADS.JDM
QSORT DOORS.JDM
JMSTAT JMSTAT.CFG -O-11/01/92
This first reads in the new data, then the Qsort program sorts
each of the database files, then the last line deletes any duplicate
lines and also removes any entries prior to Nov 1st, 1992.
The file that is used to provide the color codes to the program
is called DISPLAY.CLR. If this file exists, the system will use it
to enhance the output display files. The format for it is fairly
simple. Lines 1 and 2 are used for the display heading. Line 3 is
used for all borders. Lines 4 through 9 are used as column headings
and the lines from 10 through 15 are used for the actual data. Line
16 is the code that is printed before the start of the display, and
can be used to clear the screen or do a nopause. Line 17 is an
ending code and could be used to pause the screen. Each line should
contain just one color code. It could either be a Wildcat! color
code or an ANSI color sequence, whichever you prefer.
There is a sample DISPLAY.CLR file included in this package, so if
you do not wish to use color, either delete or rename this file.
12
JMSTATS ver 2.0
SUPPORT
This program will be supported through ANDROID II BBS, where I
am the sysop. The numbers for the BBS are (404) 978-6736 which is a
2400 baud line and (404) 978-9636 which is a 14,400 v.32bis modem.
Leave a message to Joe Martin in the JMSTATS support conference. If
you have an emergency problem, you can try paging the sysop. I am
also considering setting up a voice support line for registered
sysops, but that will have to wait until I can find out what kind of
impact the program will have.
13
JMSTATS ver 2.0
DATABASE FILES
For those that may find an interest or wish to write their
own reports from the databases built by JMSTATS, I am including a
detail summary of the layout of these files. These are the files
with the extension of JDM.
CALLS
position description
1 - 8 The date of the call.
9 - 13 The time of the call.
14 - 16 Amount of time spent on-line.
17 The type of exit the user made (normal, dropped, etc.)
18 Whether fast login was used.
19 Whether a new files scan was done.
20 Whether the caller uploaded replies using Tomcat!
21 Whether the caller downloaded messages using Tomcat!
22 Whether the caller paged the sysop.
23 - 42 Caller's name.
43 - 52 Caller's security level.
UPLOADS
position description
1 - 8 The date of the call.
9 - 13 The time of the call.
14 - 18 Baud rate of the call.
19 Whether the connection was MNP.
20 - 31 The filename of the upload.
32 - 41 The protocol used to upload the file.
42 - 44 The file area that it was uploaded to.
45 - 64 Caller's name.
65 - 74 Caller's security level.
DOWNLOADS
position description
1 - 8 The date of the call.
9 - 13 The time of the call.
14 - 18 The baud rat of the call.
19 Whether the connection was MNP.
20 - 23 The CPS of the transfer.
24 - 35 The filename of the download.
36 - 45 The protocol used for the transfer.
46 - 48 The file area downloaded from.
49 - 68 Caller's name.
69 - 77 Caller's security level.
14
JMSTATS ver 2.0
MESSAGES
position description
1 - 8 The date of the call.
9 - 13 The time of the call.
14 - 17 The message area the the message was entered in.
18 - 37 Caller's name.
38 - 47 Caller's security level.
DOORS
position description
1 - 8 The date of the call.
9 - 13 The time of the call.
14 - 15 Amount of time spent in the door.
16 - 18 The door number.
19 - 38 Caller's name.
39 - 48 Caller's security level.
CONFIG FILE
An example of a config file is shown here with
explanations.
C:\JMSTATS\
C:\WC30\ACTIVITY.001
C:\JMSTATS\DOWNLOAD.BBS
1200
2400
9600
14400
Xmodem
Xmodem/CRC
Xmodem/1KG
Ymodem
Ymodem/G
Zmodem
HS-Link
Moby-Turbo
50
150
C:\JMSTATS\SECURITY.BBS
C:\JMSTATS\FILENAME.BBS
C:\JMSTATS\CALLER.BBS
C:\JMSTATS\DOORSTAT.BBS
C:\JMSTATS\TOPFILES.BBS
C:\JMSTATS\TIMEODAY.BBS
15
JMSTATS ver 2.0
C:\JMSTATS\AREASTAT.BBS
C:\JMSTATS\TOPCALLS.BBS
C:\JMSTATS\TOPDOWN.BBS
--------------------------------------------------------------------
WARNING!!!! All lines above this must be there or the program will
not run properly if at all.
Definition of what the above configuration paramters mean:
1...This is the path to where the data files are to be stored. By
having multiple configuration files with different directories
in this field, you can maintain separate databases for such
things as different nodes or different lengths of data
retention.
2...This is the full path and filename of the ACTIVITY log that you
will be reading from. This is where WILDCAT! stores the
information this program reads it's information from.
3...This is the full path and filename where the DOWNLOADS output
display will go. This could either be in the form of a bulletin
or Hello file or it could be a file stored somewhere else.
Leaving this line blank will force the output to go to the
screen, but with no pauses at this time. Putting PRN in this
line will send the output to the printer.
4-11...These lines are the baud rates that will be displayed on the
download display. These must EXACTLY match the baud rates that
show up in your activity log. There are 8 lines for these and
they will appear in the exact order you enter them in this
configuration file. Normal screen width would allow only 4
different baud rates. Of course, you may fill in more if you are
storing as a disk file that will not be used as a bulletin or
hello screen, or if you are sending the output to a printer that
can handle more than 80 characters per line. Leave all other
lines as blank lines within these lines so the program will
truncate the display properly.
12-21...These lines contain the file transfer protocols that will
appear in the download output. These must EXACTLY match the way
they appear in your activity log file. The output will take any
other downloads that do not match these and group them in a
protocol called 'OTHER PROTOCOLS' so that they will be included
in the display after the ones you have defined. The output will
contain these protocols in the exact order that you enter them.
In order to fit on a standard single screen, I would recommend
only putting in 5 protocols as it will add the OTHER PROTOCOLS
to the bottom of the display. Enter your most popular file
transfer protocols on these lines. Leave all other lines as
blank lines within these lines so the program will truncate the
display accordingly.
22...This line contains the Minimum percentage of cps that you wish
to include in the display and the average cps calculation. For
example, if you have this line set at 50, then a file transfer
for a 2400 baud caller would only be included if his cps was
greater than 120. This will prevent those occasional file
transfers where the caller had a problem either on his end or
with the file and will not use these figures.
16
JMSTATS ver 2.0
23...This line contains the Maximum percentage of cps that you wish
to include in the display and the average cps calculation. For
example, if you have this line set at 150, then a file transfer
for a 2400 baud caller would only be included if his cps was
less than 360. This will prevent those occasional file
transfers where the activity log shows some strange figure
because of recovery mode on a file transfer from showing up in
the display and affecting the average cps.
24...This line is the full path and filename of the output file for
the Security level display. This can be PRN to output to the
printer, or left blank to output to the screen. Like the
download display, this can also be used as a bulletin or Hello
file.
25...This line is the full path and filename of the output file for
the Filename display. This can be PRN to output to the printer,
or left blank to output to the screen. This option is not
intended to be used as a bulletin or hello file.
26...This line is the full path and filename of the output file for
the caller display. This can be PRN to output to the printer, or
left blank to output to the screen. This option is not intended
to be used as a bulletin or hello file.
27...This line is the full path and filename of the output file for
the Door statistics display. This can be PRN to output to the
printer, or left blank to output to the screen. This option can
be used as a bulletin or Hello screen.
28...This line is the full path and filename for the output file for
the TOPFILES display. This can be PRN to output to the printer,
or left blank to output to the screen. This option can be used
as a bulletin or Hello screen.
29...This line is the full path and filename for the output file for
the Time of Day display. This can be PRN to output to the
printer, or left blank to output to the screen. This option can
be used as a bulletin or Hello screen.
30...This line is the full path and filename for the output file for
the file and message area statistics display. This can be PRN to
output to the printer, or left blank to output to the screen.
This option can be used as a bulletin or Hello screen.
31...This line is the full path and filename for the output file for
the Top Callers display file. This can be PRN to output to the
printer, or left blank to output to the screen. This option is
especially useful as a bulletin or Hello screen.
32...This line is the full path and filename for the output file for
the Top Downloaders display file. This can be PRN to output to the
printer. or left blank to output to the screen. This option is
especially useful as a bulletin or Hello screen.
17